Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cleanup feature code after mainnet-beta activation #34289

Merged
merged 2 commits into from
Dec 13, 2023

Conversation

tao-stones
Copy link
Contributor

Problem

feature EfhYd3SafzGT472tYQDUc4dPd2xdEfKs5fwkowUgVt4W Remove support for RequestUnitsDeprecated instruction #27500 activated everywhere.

Summary of Changes

  • Cleanup feature code
  • Update/remove tests on that feature gate

Fixes #

Copy link

codecov bot commented Nov 30, 2023

Codecov Report

Merging #34289 (965dafd) into master (71c1782) will decrease coverage by 0.1%.
Report is 4 commits behind head on master.
The diff coverage is 100.0%.

Additional details and impacted files
@@            Coverage Diff            @@
##           master   #34289     +/-   ##
=========================================
- Coverage    81.9%    81.9%   -0.1%     
=========================================
  Files         819      819             
  Lines      219884   219759    -125     
=========================================
- Hits       180263   180122    -141     
- Misses      39621    39637     +16     

Copy link
Contributor

@apfitzge apfitzge left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Few initial comments, but as you mentioned this will not be merged until future version.

sdk/src/compute_budget.rs Outdated Show resolved Hide resolved
@@ -5,8 +5,6 @@ type MicroLamports = u128;

pub enum PrioritizationFeeType {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we plan to introduce more variants of prioritization in the near future?
If not, imo we should just get rid of this enum entirely.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, I agree. Didn't want to do it in "feature cleanup" PR. Would like to do it when this pr is merged. Given it's take some time before landing the cleanup PR, dont know what's the best way to remind myself to refactor tho 🤔

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe just an issue?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tao-stones tao-stones marked this pull request as ready for review December 12, 2023 22:46
@tao-stones tao-stones merged commit 39f2866 into solana-labs:master Dec 13, 2023
43 checks passed
@tao-stones tao-stones deleted the cleanup-feature-27500 branch December 13, 2023 00:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants